Release Notes (Readme.htm)
Microsoft Windows Resource Kit Tools

This document contains important information that is not included in Help for the Microsoft® Windows® Resource Kit Tools, including how to install the tools, along with important updates and corrections.

Contents

About the Tools

Setup for the Resource Kit Tools

General Setup Instructions

Installing from the Command Prompt

Unattended Installation

Former Resource Kit Tools Now Included in the Support Tools or Operating System

Support Tools

Operating System

Resource Kit Support Policy

Individual Tool Release Notes

Acctinfo.dll: Additional Account Information Properties Page

Custreasonedit.exe: Custom Reason Editor

Dnsdiag.exe: DNS Resolver Tool

Lockoutstatus.exe: Account Lockout Status

Regview.exe: Registry Viewer Tool

Timeit.exe

About the Tools

The Windows Resource Kit Tools are intended to assist experienced users in diagnosing and resolving computer problems, and to enhance the management capabilities of the operating system. For tools documentation, see Windows Resource Kit Tools Help (Rktools.chm).

For the most current information about the Windows Resource Kit Tools, see the Windows Deployment and Resource Kits Web site.

Setup for the Resource Kit Tools

The Windows Resource Kit Tools are located in the \Rktools folder of the Windows Server 2003 Deployment Kit companion CD. Rktools.msi, a Windows Installer package, installs all of the Resource Kit Tools and documentation onto your computer's hard disk.

Important

These tools have not been localized: they are written and tested in English only. Using these tools with a different language version of the operating system can produce unpredictable results.

General Setup Instructions

The Windows Resource Kit Tools can be installed on computers running the Windows Server 2003 or the Windows XP Professional operating systems. The Resource Kit Tools Setup program cannot be used to upgrade previous versions of the Resource Kit Tools.

Installing the Windows Resource Kit Tools

Important

It is highly recommended that you remove all previous versions of the Resource Kit Tools, including beta versions, before running the Resource Kit Tools Setup program.

1. Insert the Microsoft Windows Server 2003 Deployment Kit companion CD in your CD drive.
2. Click Install the Resource Kit Tools.

Setup installs Windows Resource Kit Tools files onto your hard disk. A typical installion requires 37 megabytes (MB) of free space.

By default, Setup installs the tool files into the \Program Files\Windows Resource Kits\Tools folder, although it allows you to choose another location. However, Setup installs Tools Help (Rktools.chm) into \%windir%\Help regardless of where you choose to install the tool files.

Setup also adds the folder \Program Files\Windows Resource Kits\Tools (or the folder name you choose for installing the tools) to your computer's system PATH statement.

Setup creates a Programs | Windows Deployment and Resource Kits | Windows Resource Kits | Tools folder on the Start menu. The folder contains shortcuts to the command shell, Tools Help, and Tools Help Readme.

To find the Windows Resource Kit Tools Help in Help and Support Center, on the Help and Support Center home page, under Support Tasks click Tools.

Some Resource Kit Tools require separate or additional setup besides the steps described earlier. For more information about each of these tools and others with additional requirements, see Windows Resource Kit Tools Help (Rktools.chm).

Note

On the Windows Server 2003 Deployment Kit companion CD, the tools are included in the Rktools.msi file. You cannot run executable files, call other binaries, or open documentation directly from an .msi file. Be aware also that for some tools, the Resource Kit Setup program or the tool's own Setup program performs other installation procedures such as making changes in the registry. You must first install the tools on your hard disk with Resource Kit Tools Setup before running them.

Installing from the Command Prompt

You can install the Windows Resource Kit Tools from the command prompt. For example, to install the Resource Kit Tools in the default directory, insert the Windows Server 2003 Deployment Kit companion CD in your CD drive and type the following at the command prompt:

msiexec /i cd_drive_letter:\rktools\rktools.msi

where cd_drive_letter: is the letter indicating the CD drive (for example, d:).

For more information about the syntax of the Windows Installer client-side installer service (Msiexec.exe), search for "msiexec" in Help and Support Center.

Unattended Installation

To perform an unattended installation of the Windows Resource Kit Tools, insert the Windows Server 2003 Deployment Kit companion CD in your CD drive and type the following at the command prompt:

msiexec /i cd_drive_letter:\rktools\rktools.msi /q

where cd_drive_letter: is the letter indicating the CD drive (for example, d:).

Former Resource Kit Tools Now Included in the Support Tools or Operating System

A number of tools that shipped in previous versions of the Windows Resource Kits are now included in the Windows Support Tools or in the Windows Server 2003 operating system.

Support Tools

The following former Windows Resource Kit Tools are now included in the Support Tools for Windows Server 2003 and Windows XP, which are located in the \Support\Tools folder of the operating system CD but must be installed separately from the operating system. Support Tools Help (Suptools.chm) is installed with the Support Tools.

Operating System

The following former Windows Resource Kit Tools are now included in the Windows Server 2003 operating system. For more information about these tools, in Help and Support Center, click Tools, and then click Command-line reference A-Z.

Resource Kit Support Policy

The SOFTWARE supplied in the Windows Resource Kit Tools is not supported under any Microsoft standard support program or service. Customers can, however, report issues and bugs by sending e-mail to rkinput@microsoft.com. Microsoft will, at its sole discretion, address issues and bugs reported in this manner, and responses are not guaranteed. This e-mail address is only for issues related to the Windows Resource Kit Tools and the Windows Deployment and Resource Kits.

The SOFTWARE (including instructions for its use and all printed and online documentation) is provided "AS IS" without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the SOFTWARE and documentation remains with you.

In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the SOFTWARE be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the SOFTWARE or documentation, even if Microsoft has been advised of the possibility of such damages.

For more information about Windows Server 2003 and the Windows Server 2003 Deployment and Resource Kits, visit the Windows Deployment and Resource Kits Web site.

© Copyright 1985û2003 Microsoft Corporation. All rights reserved.

Individual Tool Release Notes

The following section includes information about individual Windows Resource Kit Tools that are not covered in Windows Resource Kit Tools Help (Rktools.chm).

Acctinfo.dll: Additional Account Information Properties Page

Acctinfo.dll is a dynamic link library that, when registered on a computer, adds a new property page (Additional Account Info) to the user object Properties dialog box in Active Directory Users and Computers. This new property page displays information such as the date when a user's password was last set, the date when a user's password will expire, and the dates and times when a user last logged on and logged off. This information is not typically available in Active Directory Users and Computers, for one of two reasons:

• In some cases, the information is not actually stored in Active Directory, but instead is calculated only when needed. For example, the date that a user's password will expire is not stored in Active Directory; instead, Active Directory stores the date that the password was last set and the maximum allowed password age (for example, passwords must be set every 60 days). To determine the actual date that a password expires, you typically have to use scripts to retrieve this information and calculate the expiration date. Acctinfo.dll performs these calculations for you.
• In some cases, information is stored locally rather than in Active Directory. For example, last logon and last logoff times are stored on each individual domain controller and are not replicated throughout the domain. Acctinfo.dll enables you to determine the last time a user logged on or logged off from a specified domain controller. If users are typically authenticated by the same domain controller, this will tell you when these users last logged on to or logged off from the domain. If users are authenticated by multiple domain controllers, you will need to install Acctinfo.dll on each of these servers and check the account information on each one.

Acctinfo.dll is primarily designed to report information about user passwords, account status, and logons. However, it also includes a mechanism for changing user passwords and for unlocking locked user accounts.

Concepts

Acctinfo.dll adds a custom property page to the user account object Properties dialog box in Active Directory Users and Computers. For more information about Active Directory Users and Computers, see Help and Support Center for Windows Server 2003.

System Requirements

The following are the system requirements for this tool:

• Windows Server 2003 or Windows 2000 Server operating system
• You must be an Administrator to install Acctinfo.dll.

File Required

• Acctinfo.dll

AcctInfo.dll Remarks

Installing Acctinfo.dll

To access the custom property page provided by Acctinfo.dll, you must first install and register the file Acctinfo.dll.

To install and register Acctinfo.dll

1. Copy the file Acctinfo.dll to the %windir%\system32 folder. In Windows Server 2003, this is typically C:\Windows\System32. In Windows 2000, this is typically C:\Winnt\System32.
2. Open a command window, and type the following (this example assumes that your %windir%\system32 folder is C:\Windows\System32):
   

   regsvr32 c:\windows\system32\acctinfo.dll

If the command is successful, a dialog box appears informing you that Acctinfo.dll has been registered.

Note

Acctinfo.dll must be registered on each computer on which Active Directory Users and Computers is used to access user account information. For example, suppose you have two servers (Server A and Server B) commonly used to display user account information. If you register Acctinfo.dll on Server A, the Additional Account Info property page will be available in Active Directory Users and Computers. However, this property page will not be available in Active Directory Users and Computers on Server B. To access this property page on Server B, you must register Acctinfo.dll on Server B.

Removing Acctinfo.dll

You can remove the Additional Account Info property page from Active Directory Users and Computers by uninstalling Acctinfo.dll. To uninstall Acctinfo.dll, open a command window, and type the following (this example assumes that your %windir%\system32 folder is C:\Windows\System32):

regsvr32 /u c:\windows\system32\acctinfo.dll

If the command is successful, the file Acctinfo.dll will be removed, and the Additional Account Info property page will no longer be visible in Active Directory Users and Computers. Note that this removes only the custom property page, and does not affect the data displayed on that page. This information (such as last logon and last logoff) can still be retrieved by other means.

Acctinfo.dll UI

Information retrieved by Acctinfo.dll must be viewed in Active Directory Users and Computers. To view information for a specified account, open Active Directory Users and Computers (either by using the Start menu or by typing dsa.msc in the Run dialog box). Locate and double-click the appropriate user account. In the Properties dialog box, click the Additional Account Info tab.

The Additional Account Info property page displays the following attribute values:

Additional Account Info Property Page

Modifying User Account Properties from the Additional Account Info Property Page

Although Acctinfo.dll is primarily designed to display information, it also allows you to perform two commonly required tasks: changing a user's password, and unlocking a locked user account.

Changing a User's Password

1. On the Additional Account Info property page, click Set PW On Site DC.
2. In the Change Password on a DC in the Users Site dialog box, type a new password in the Password and Confirm Password text boxes. Optionally, you can also select User Must Change Password At Next Logon. If selected, the user will be able to use their new password to logon to the domain, but will then be prompted to change their password.
3. Click OK.

You must have the right to reset user passwords for this operation to succeed. If you do not have this right, you will still be able to access the Change Password on a DC in the Users Site dialog box. However, after making the changes and clicking OK, an error message will be displayed, and the password will not be changed.

Unlocking a Locked User Account

1. On the Additional Account Info property page, click Set PW On Site DC.
2. In the Change Password on a DC in the Users Site dialog box, type a new password in the Password and Confirm Password text boxes. You cannot unlock a user account in this dialog box without setting a password as well.

   Caution

   You can select the Unlock Account check box by clicking both the Password and Confirm Password text boxes without typing anything. However, this will result in the user no longer having any password (because the two password boxes will be blank).

3. Select the Unlock Account check box.
4. Click OK.

Custreasonedit.exe: Custom Reason Editor

Custom Reason Editor (CustReasonEdit) is a command-line and GUI tool that allows users to add, modify, and delete custom reasons used by the Shutdown Event Tracker on the Windows Server 2003 operating system. There are two ways to use this tool: Use the command line to perform basic importing and exporting of custom reasons to a registry file, or use the GUI to perform all other types of custom reason editing. CustReasonEdit includes a set of sample reasons to help you get started.

Concepts

Shutdown Event Tracker helps system administrators track reasons for system down-time by collecting these reasons at the time of shutdown and logging this data to the event log. For more information about the Shutdown Event Tracker component, see Help and Support Center.

System Requirements

The following are the system requirements for this tool:

• Windows Server 2003 operating system.
• You must be an Administrator on the local computer.

File Required

• Custreasonedit.exe
• Samplereasons.reg

CustReasonEdit Remarks

Reviewing Best Practices

Use the table below to identify best practices you should use when working with custom reasons.

Installing the Sample Reason Package

To use the sample reasons included with CustReasonEdit, you must install them first.

To install the sample reason package:

1. Navigate to the folder where the Resource Kit Tools are installed.
2. Right-click the file Samplereasons.reg, and then click Merge on the shortcut menu.

This adds the set of sample reasons to the local system.

Note

Installing the sample reason package will also disable built-in reasons. For more information, see "Disabling Built-in Reasons" later in this topic.

Localizing Custom Reasons

The Shutdown Event Tracker displays custom reasons corresponding to the system locale, not the user locale. For more information about System Locale, see Help and Support Center. CustReasonEdit stores custom reasons for the system locale on the host system; however, it accepts input in any language. For example, if the user creates custom reasons by using Japanese characters on an English language version system, these reasons will be displayed in Japanese characters by the Shutdown Event Tracker on the English language version system, as long as the necessary code page is installed in the operating system.

Testing Custom Reasons

On a system on which the Shutdown Event Tracker is enabled, you can test custom reasons created by CustReasonEdit. Click Shut Down on the Start menu. The Shut Down Windows dialog box should display the custom reasons you created.

Deploying Custom Reasons

Use CustReasonEdit to create well-formed custom reasons on a single computer. The following list describes several options for deploying these reasons to a wider range of computers.

• A file can be exported by using the command-line export command, and this file can then be imported by CustReasonEdit on every system.
• The GUI can be used to connect to each system and populate the custom reasons.
• Group Policy can be used to propagate the registry subkey where custom reasons are stored. To accomplish this, use Group Policy to propagate the following subkey and all of its entries:

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability\UserDefined

Disabling Built-in Reasons

You can exclude built-in reasons from the Shutdown Event Tracker list and use custom reasons only. In the registry editor Regedit.exe, navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability\ShutdownIgnorePredefinedReasons

Create the registry entry ShutdownIgnorePredefinedReasons with the data type DWORD, and the value set to 1.

To re-enable built-in reasons, set the value of the entry ShutdownIgnorePredefinedReasons to 0.

CustReasonEdit Syntax

custreasonedit [/i] [/l] [/e FileName] [/r FileName] [/s] [/m Host] [/?]

Parameters

/i

Opens the GUI window for complete editing of shutdown reasons.

/l

Lists the existing shutdown reasons.

/e FileName

Exports the custom reason subkey to a registry file named FileName.

/r FileName

Imports the custom reason subkey to a registry file named FileName.

/s

Runs CustReasonEdit using the system locale for custom reasons.

/m Host

Allows you to connect to a remote system to import or export custom reasons

/?

Displays command-line usage.

CustReasonEdit UI

To access the GUI you must type the following at a command prompt: custreasonedit /i. By default, the list of custom reasons are populated with the list of custom reasons installed on the local system. For information about the reason attributes such as Planned, Expected Shutdown, and Unexpected Shutdown, see the Shutdown Event Tracker documentation in Help and Support Center.

CustReasonEdit contains the following windows:

Custom Reason Editor window

Switch to Another Computer window

CustReasonEdit Example

Add a Custom Reason

The task in this example is to use the CustReasonEdit UI to add a custom reason.

1. Type the following at the command line:
   

   custreasonedit /i

2. Press ENTER. The Custom Reason Editor window opens.
3. Under Reason Category, select a reason category corresponding to the major category of the default reasons used by Windows.
   • If this reason should be used for planned shutdowns, select the Planned check box.
   • If this reason requires users to add a comment before they can shut down the computer, select the Comment Required check box.
   • To indicate whether this reason should be displayed in the Unexpected Shutdown or Expected Shutdown dialog boxes, select at least one of the Unexpected Shutdown and Expected Shutdown check boxes.
4. In the Minor Code box, enter a number between 1 and 1000 that is different from an existing minor code. Minor codes are created based on the combination of the following attributes: Reason Category, Planned, Unexpected Shutdown, and Expected Shutdown.
5. In the Title box, type a title for the reason category in 64 characters or less.
6. In the Description box, type a detailed description of the reason in 256 characters or less.
7. Click Add to add the reason to the system.

Dnsdiag.exe: DNS Resolver Tool

DNS Resolver Tool (DNSDiag) is a command-line tool that allows you to troubleshoot e-mail delivery problems caused by Domain Name System (DNS) issues. DNSDiag simulates the Simple Mail Transfer Protocol (SMTP) service's internal code-path and displays diagnostic messages that indicate how the DNS resolution is proceeding. DNSDiag must be run on the computer where the DNS problems are occurring.

Note

You can use DNSDiag on a server running Windows Server 2003 that is running the SMTP service without Exchange installed.

System Requirements

The following are the system requirements for this tool:

• Windows Server 2003 operating system.
• You must be an Administrator on the local computer if you want DNSDiag to simulate a specific virtual server instance.

File Required

• Dnsdiag.exe

DNSDiag Syntax

%WINDIR%\system32\inetsrv\dnsdiag HostName [/d] [/v #] [/s ServerList] [/p Protocol] [/a] [/?]

Parameters

HostName

Specifies the host name that you want to resolve. HostName is the fully-qualified domain name of the target for the queue where errors are occurring. This name might be different from the name displayed in the SMTP queue in Exchange System Manager.

/d

Runs DNSDiag in debug mode. If this switch is specified, DNSDiag generates verbose output. Debug mode creates generates a great deal of output, and the most critical messages are highlighted in a different color. When this switch is not specified, only the critical messages are generated. the tool generates verbose output.

/v #

Identifies a specific virtual server instance that DNSDiag simulates. For example, if you want DNSDiag to simulate the first virtual server on an Exchange server, type /v 1.

Notes

• You must close all files in the cache before using this parameter. Otherwise, you will get an error message stating that the requested resource is in use.
• You must be an Administrator on the local computer to use this parameter.
• After DNSDiag reads the external DNS server list for that specific virtual server instance, it queries that server list for HostName, where HostName is an external host. If HostName is the name of an Exchange server, the query is generated against the default DNS servers for the local computer.
• If you are running DNSDiag on an Exchange server in a perimeter network, DNSDiag detects this situation and uses the external DNS servers configured on the virtual server.

/s ServerList

Lists the DNS servers' IP addresses in dotted decimal notation. Use this switch if you want to specify a specific set of servers. If this switch is not specified, the default DNS servers on the local computer are used as specified by the /v switch. Separate server IP addresses with a space or a tab character.
Note
You cannot use this switch with the /v switch.

/p Protocol

Allows you to use a protocol different from the one configured in the metabase. If this switch is not specified, the protocol configured in the metabase for smtpsvc/SmtpUseTcpDns is used. You can use the following values:
TCP generates a TCP-only query.
UDP generates a UDP-only query.
DEF generates a default query that will initially query a server with UDP, and then—if that query results in a truncated reply—it will be retried with TCP.
Note
You cannot use this switch with the /v switch.

/a

Runs DNSDiag in a mode where all the DNS servers obtained (either through the registry, Active Directory, or the /s switch) are queried in sequence and all query results are displayed.

/?

Displays command-line usage.

DNSDiag Examples

Example: Resolve an External Host by Using Specific DNS Servers

The task in this example is to use DNSDiag to resolve the external host with a DNS name of example.com by using the DNS servers with the IP address 127.1.0.1. and 127.1.10.8.

Type the following at the command line:

%WINDIR%\system32\inetsrv\dnsdiag example.com -s 127.1.0.1     127.1.10.8

Note

DNSDiag uses error codes that are set at the ERROR LEVEL for use in batch files. Use the following descriptions to understand the DNSDiag return codes:

Lockoutstatus.exe: Account Lockout Status

Overview

Account Lockout Status (LockoutStatus) is a combination command-line and GUI tool that displays lockout information about a particular user account. LockoutStatus collects information from every contactable domain controller in the target user account's domain.

File Required

• Lockoutstatus.exe

LockoutStatus Syntax

lockoutstatus {/u:DomainName\UserName | /u:UserName@DomainName} [/?]

DomainNam

Target NetBIOS or DNS domain name

UserName

Target user name

LockoutStatus GUI

File Menu

The File menu allows the target user and domain to be changed. This menu also allows the output of LockoutStatus to be saved in text format.

View Menu

The View menu allows the user to view the status of the target users password. This menu also alows the user to refresh the main window of LockoutStatus.

Regview.exe: Registry Viewer Tool

Registry Viewer Tool (RegView) is a command-line tool that allows you to view Group Policy Registry.pol files without applying them to the registry.

Concepts

Registry.pol Files

The Administrative Templates extension of Group Policy saves information in the Group Policy template in text files with the name Registry.pol. These files contain the customized registry settings that are applied to the Machine or User portion of the registry, which you specify by using Group Policy Object Editor. The Windows 2000 Registry.pol file is analogous to the Windows 95 or Windows 98 Config.pol file and the Windows NT® 4.0 NTConfig.pol file.

Two Registry.pol files are created and stored in the Group Policy template—one for Computer Configuration, which is stored in the \Machine subdirectory, and one for User Configuration, which is stored in the \User subdirectory.

Note

The format of the .pol files in the Group Policy template differs from that of the .pol files in previous versions of Windows.

The .pol files created by Windows NT 4.0 and Windows 95 can be applied only to the operating system on which they were created. The .pol file produced by the Windows NT 4.0 System Policy Editor was a binary file, whereas the Registry.pol file produced by the Administrative Templates node of Group Policy Object Editor is a text file with embedded binary strings.

System Requirements

The following are the system requirements for this tool:

• Windows Server 2003 or Windows 2000 operating system.
• You must be an Administrator on the local computer.

File Required

• Regview.exe

RegView Syntax

regview PathName\registry.pol

PathName

Specifies the complete path to the directory containing the Registry.pol files that you want to view.

RegView Examples

Example: View a Registry.pol file

The task in this example is to use RegView to view a Registry.pol file.

Type the following at the command line:

regview c:\registry.pol

Output similar to the following is displayed:

KeyName:        Software\Policies\Microsoft\SystemCertificates\EFS
ValueName:      EFSBlob
ValueType:      REG_BINARY
Value:
01 00 01 00 01 00 00 00 77 02 00 00 73 02 00 00
00 00 00 00 00 00 00 00 01 05 00 00 00 00 00 05
15 00 00 00 96 81 73 8c ab 8b 00 94 b3 36 4b 6a
f4 01 00 00 30 82 02 37 30 82 01 a4 a0 03 02 01
02 02 10 66 f1 c8 25 99 9c 84 8d 42 65 f5 cd 3c
fa 5c b5 30 09 06 05 2b 0e 03 02 1d 05 00 30 50
31 16 30 14 06 03 55 04 03 13 0d 41 64 6d 69 6e
69 73 74 72 61 74 6f 72 31 0c 30 0a 06 03 55 04
07 13 03 45 46 53 31 28 30 26 06 03 55 04 0b 13
1f 45 46 53 20 46 69 6c 65 20 45 6e 63 72 79 70
74 69 6f 6e 20 43 65 72 74 69 66 69 63 61 74 65
30 1e 17 0d 30 33 30 33 33 31 31 39 32 39 30 36
5a 17 0d 30 36 30 33 33 30 31 39 32 39 30 36 5a
30 50 31 16 30 14 06 03 55 04 03 13 0d 41 64 6d
69 6e 69 73 74 72 61 74 6f 72 31 0c 30 0a 06 03
55 04 07 13 03 45 46 53 31 28 30 26 06 03 55 04
0b 13 1f 45 46 53 20 46 69 6c 65 20 45 6e 63 72
79 70 74 69 6f 6e 20 43 65 72 74 69 66 69 63 61
74 65 30 81 9f 30 0d 06 09 2a 86 48 86 f7 0d 01 
01 01 05 00 03 81 8d 00 30 81 89 02 81 81 00 b7
94 55 3d 85 39 02 47 bc 64 82 08 33 60 85 36 09
a6 08 99 71 e1 fe 79 2a e0 25 84 c3 ca 28 22 97
9d fd ca 49 8d 14 1d 20 f6 81 f9 0f 47 ed cf 7c
eb e5 ad 74 e4 d4 01 ea 2b a4 4e 9b 09 19 16 05
KeyName:        Software\Policies\Microsoft\SystemCertificates\EFS\Certificates\
B7140ABD7B323D6143C57395BE8867D366EAACCD
ValueName:      Blob
ValueType:      REG_BINARY
Value:
03 00 00 00 01 00 00 00 14 00 00 00 b7 14 0a bd 
7b 32 3d 61 43 c5 73 95 be 88 67 d3 66 ea ac cd
02 00 00 00 01 00 00 00 c4 00 00 00 1c 00 00 00 
6c 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 01 00 00 00 65 00 37 00 39 00 64 00
61 00 34 00 37 00 65 00 2d 00 34 00 33 00 39 00
39 00 2d 00 34 00 31 00 63 00 32 00 2d 00 38 00
39 00 37 00 35 00 2d 00 62 00 63 00 34 00 38 00
34 00 61 00 31 00 37 00 39 00 37 00 31 00 34 00
00 00 00 00 00 00 00 00 4d 00 69 00 63 00 72 00
6f 00 73 00 6f 00 66 00 74 00 20 00 42 00 61 00
73 00 65 00 20 00 43 00 72 00 79 00 70 00 74 00
6f 00 67 00 72 00 61 00 70 00 68 00 69 00 63 00
20 00 50 00 72 00 6f 00 76 00 69 00 64 00 65 00
72 00 20 00 76 00 31 00 2e 00 30 00 00 00 00 00
20 00 00 00 01 00 00 00 3b 02 00 00 30 82 02 37
30 82 01 a4 a0 03 02 01 02 02 10 66 f1 c8 25 99
9c 84 8d 42 65 f5 cd 3c fa 5c b5 30 09 06 05 2b
0e 03 02 1d 05 00 30 50 31 16 30 14 06 03 55 04
03 13 0d 41 64 6d 69 6e 69 73 74 72 61 74 6f 72
31 0c 30 0a 06 03 55 04 07 13 03 45 46 53 31 28
30 26 06 03 55 04 0b 13 1f 45 46 53 20 46 69 6c
65 20 45 6e 63 72 79 70 74 69 6f 6e 20 43 65 72
74 69 66 69 63 61 74 65 30 1e 17 0d 30 33 30 33
33 31 31 39 32 39 30 36 5a 17 0d 30 36 30 33 33

KeyName:        Software\Policies\Microsoft\SystemCertificates\EFS\CRLs
ValueName:
ValueType:      REG_NONE
Value:          This key contains no values
 
KeyName:        Software\Policies\Microsoft\SystemCertificates\EFS\CTLs
ValueName:
ValueType:      REG_NONE
Value:          This key contains no values

Timeit.exe

TimeIt is a command-line tool that records the time a specified command takes to run.

File Required

• Timeit.exe

TimeIt Syntax

timeit [-f FileName] [-a] [-c] [-i] [-d] [-s] [-t] [-k KeyName | -r KeyName] [-m Mask] [Command]

-f FileName

Specifies the name of the database file where TimeIt keeps a history of previous timings. The default file name is .\Timeit.dat

-k KeyName

Specifies the keyname to use for this timing run.

-r KeyName

Specifies the key name to remove from the database. If the key name is followed by a comma and a number, the slowest time (positive number) or the fastest time (negative number) for that key name will be removed.

-a

Specifies that TimeIt should display average of all timings for the specified key name.

-i

Ignores nonzero return codes from the program run by TimeIt.

-d

Shows detail for average.

-s

Suppresses systemwide counters.

-t

Specifies tabular output.

-c

Forces a re-sort of the database.

-m Mask

Specifies the processor affinity mask.

Command

Specifies the command to time.

Note

TimeIt accepts only parameters preceded with a dash (-).